Windows Print Scout Overview
The Print Scout monitors printing activity throughout an organization or specific ranges within an organization. You can install the Print Scout on print servers and user workstations (for Print Analytics) and on workstations (for Secure Printor Secure Print Direct). Once installed, the Print Scout collects comprehensive, detailed information about each print job, including who submitted it, when it was submitted, which print device was used, and so on. This information is sent to the HP Insights server for real-time analysis and reporting capability.
MSI Installer
Starting with Print Scout 8.1, the installer is now delivered as an MSI package instead of the previous EXE format. This change improves compatibility with enterprise deployment tools and simplifies automated installations and updates.
-
Simplifies mass deployment and supports silent installation, making it ideal for enterprise use.
-
Supports centralized deployment tools like SCCM or Group Policy
-
Fully compatible with Windows 11 and ARM64 devices, future proofing deployments
-
MSI packages are digitally signed, support encrypted logging, and align with Windows Protected Print (WPP) standards.
-
Simplifies uninstallation. Administrators can choose between a simple graphical method through Windows Settings or Control Panel, or a command-line approach for advanced scenarios.
-
Can upgrade existing EXE based installations.
Note: For a complete list of command-line properties available for the MSI installer, please refer to the Print Scout MSI Installer Properties document. It includes detailed descriptions and usage examples for each supported parameters relevant to Print Scout deployments.
Collected Data
The Print Scout collects the following data about each print job:
- Date/Time
- Job Size (kB)
- Number of Pages
- Number of Sheets
- Number of Copies
- Paper Size
- Originals (e.g. when a job consists of multiple copies of a document, this is the number of pages in the original document.)
- Finishing Options (includes one-sided/two-sided, stapling, tray).
- Print Path (includes printer name, port name, share name, and server share name).
- The network ID of the job owner
- Application Name (e.g. Word, Excel). Application Tracking can be disabled or enabled.
- Transaction Type (direct job or secure job) - available only if you have Secure Print license
- Document Name
- The Print Scout also records the Network Name, Operating System, and Service Pack Level of each machine on which it is installed.
Installed Components
The Windows Print Scout deploys the following on user's workstations:
- Installs a queue named HP Secure Printer.
- On Windows 11 and Windows on Arm devices, the queue uses the Microsoft IPP Class Driver by default if WPP is ON.
- On Windows 10, the queue uses the HP manufacturer driver by default if WPP is OFF
- Installs two services :
- Print Scout Spooler Service which handles Secure Print printing services.
- Print Scout Service which is responsible for print tracking and related features.
- Installs the HP Secure Print desktop app that allows users to:
- View documents waiting to print
- Delete documents that they no longer need
- View activity history
- Reset PIN code
- Reset Passcode
- Offers Secure Print Failover (Offline Print). Available only if enabled
- Offers Secure Print Direct (if licensed for Secure Print Direct).
- Offers Delegate Print
Where to Deploy Print Scouts
Depending on your printing environment, the Print Scout(s) can be installed on client workstations, Windows print servers, or both. The following guidelines can help you decide where to deploy the Print Scout:
- Install the Print Scout on client workstations if you want to:
- Track direct printing to network devices
- Track printing to local devices
- Track the applications used to print (e.g. Word, Outlook)
- Collect, store, and report the user and print job information for Secure Print jobs (This requires Secure Print license)
- Allow users to print and release their jobs directly to printers (This requires HP Secure Print license)
- Install the Print Scout on a print server if:
- The majority of printing volume goes through network queues
- You want to reduce the number of installations you need to manage
- Install the Print Scout on both workstations and print servers if:
- Printing may be sent directly to printers as well as through print servers. Even though Print Scouts on workstations will track network printing, having Print Scout(s) on your print servers will enable you to collect valuable information about your print queues.
- You need to be thorough and ensure that all printing activity is tracked.
- Your print strategy or goals are still being defined and you need to collect comprehensive information about your print environment.
For information on how to install Windows Print Scout, refer to the Install Print Scout on workstation document.
Limitations and Known Issues
-
In Cloud Release, advanced finishing options such as stapling, punching, binding, etc. are not applied when a print job is submitted via the IPP Secure queue.
-
Print Scout 8.1 does not support Tenant Location Switcher - Print Scout 8.1 does not support the Tenant Location Switcher for MSI installations. If you are using a multi-tenant setup, HP strongly advises against installing or upgrading to Print Scout 8.1.
-
Watermark feature is not supported - The watermark feature is not supported on Microsoft IPP Class Driver. It's only supported on HP IPP Class Driver which is typically installed on Windows 10.
-
Direct Print: Default Printer Not Updated When Using ‘Set Default’ - Clicking “Set Default” for a direct queue in Print Scout does not reliably set it as the default printer. This may occur even when “Let Windows manage my default printer” is disabled. As a result, the chosen queue may not be used as the default when printing.
-
Uninstalling with KEEP_SETTINGS doesn't retain proxy information - Uninstalling Print Scout using the KEEP_SETTINGS=yes property removes proxy settings from the registry key. After reinstalling, the Configuration Tool does not restore these settings. If using a deployment package with InstallConfig.ini during installation, proxy settings will be automatically applied. However, if no deployment file is used, an administrator must manually re-enter the proxy settings after reinstalling.